Detect rapid consecutive taps on the same UI element and surface them as
frustration signals across the SDK:

- New RageTapDetector class tracks recent taps in a circular buffer and
  matches them by component identity (label or name+file). When N taps
  on the same target occur within a configurable time window, a
  ui.frustration breadcrumb is emitted automatically.

- TouchEventBoundary gains three new props: enableRageTapDetection
  (default: true), rageTapThreshold (default: 3), and rageTapTimeWindow
  (default: 1000ms).

- Native replay breadcrumb converters on both Android (Java) and iOS
  (Objective-C) now handle the ui.frustration category, converting it
  to an RRWeb breadcrumb event so rage taps appear on the session
  replay timeline with the same touch-path message format as regular
  ui.tap events.

- 7 new JS tests cover detection, threshold configuration, time window
  expiry, buffer reset, disabled mode, and component-name fallback.
  Android and iOS converter tests verify the new category is handled
  correctly.

- New ragetap.test.ts with 10 unit tests for RageTapDetector: threshold
  detection, different targets, time window expiry, buffer reset,
  disabled mode, custom threshold/timeWindow, component name+file
  identity, empty path, and consecutive rage tap triggers.

- 3 integration tests in touchevents.test.tsx verifying TouchEventBoundary
  wires the detector correctly: end-to-end detection, disabled prop,
  and custom threshold/timeWindow props.

- Android converter test (Kotlin) and iOS converter test (Swift) for the
  ui.frustration breadcrumb category in RNSentryReplayBreadcrumbConverter.

- Fix false-positive detection: reset tap buffer when target changes
  instead of relying on time-window pruning, which could make
  non-consecutive taps appear consecutive after interleaved taps aged
  out (Medium severity, reported by Sentry bugbot).

- Add null check for breadcrumb data in Android
  convertFrustrationBreadcrumb, matching the iOS implementation that
  already guards against nil data (Low severity).

- Remove hardcoded MAX_RECENT_TAPS buffer limit that would silently
  break detection for thresholds > 10. The buffer is now naturally
  bounded by target-change resets and time-window pruning.

- Deduplicate TouchedComponentInfo: export from ragetap.ts and import
  in touchevents.tsx instead of maintaining identical interfaces in
  both files.

- Read rage tap props at event time via updateOptions() instead of
  freezing them in the constructor, consistent with how all other
  TouchEventBoundary props are consumed.

Rename breadcrumb category from ui.frustration to ui.multiClick and
reshape the data payload to match the web JS SDK's rage click format,
so the Sentry replay timeline renders rage taps with the fire icon and
'Rage Click' label automatically.

Changes to the breadcrumb shape:
- category: ui.frustration → ui.multiClick
- type: user → default
- data.tapCount → data.clickCount
- data.type (rage_tap) removed
- data.metric: true added (marks as metric event)
- data.route added (current screen from navigation tracing)
- data.node added with DOM-compatible shape:
  tagName, textContent, attributes (data-sentry-component,
  data-sentry-source-file, sentry-label) — this allows the existing
  stringifyNodeAttributes in the Sentry frontend to render component
  names for mobile taps.

Native replay converters updated on both Android and iOS to handle
ui.multiClick instead of ui.frustration.

…sitives

When distinct child elements share a labeled ancestor, the tap identity
was based solely on the parent label, causing false rage tap detection
when tapping different controls in quick succession. Now the identity
always includes the root component name and file, even when a label is
present (e.g. label:form|name:SubmitButton|file:form.tsx).

- iOS: Add NSArray type check on path data in convertMultiClick to
  prevent runtime crash from unrecognized selector on non-array values
  (HIGH, Sentry bot).

- Clear tap buffer when detection is disabled via updateOptions to
  prevent stale taps from causing false positives on re-enable
  (LOW, Sentry bot).

- Move changelog entry from released 8.8.0 section to Unreleased
  (danger bot).

- Add time window integration test to touchevents that varies
  timestamps between taps, verifying rageTapTimeWindow actually
  excludes old taps (sentry-warden).

- Drop level: 'warning' from ui.multiClick breadcrumb to match the
  web JS SDK which defaults to info.

- Export DEFAULT_RAGE_TAP_THRESHOLD and DEFAULT_RAGE_TAP_TIME_WINDOW
  from ragetap.ts and import them in touchevents.tsx defaultProps for
  a single source of truth.

- Initialize RageTapDetector with props in the constructor and sync
  via componentDidUpdate, instead of calling updateOptions on every
  tap event.

- Remove incorrect @testonly annotation from Android
  convertMultiClickBreadcrumb since it is called from convert() in
  production code.

- Add comment explaining id: 0 placeholder in the node object (mobile
  replays don't have rrweb node IDs).

- Add tests for updateOptions: buffer cleared on disable, and
  threshold change applies immediately.

- Run yarn fix for import ordering lint.

Align with the iOS converter which validates the path type before use.
Prevents potential ClassCastException if a non-list value is passed.